Single-step custom configuration of a cloud client device

ABSTRACT

In one embodiment, a cloud client device identifies a configuration event. The cloud client device identifies a configuration associated with the configuration event. The cloud client device stores a first security key associated with the configuration and configures the cloud client device in accordance with the configuration.

TECHNICAL FIELD

This disclosure relates generally to portable information handlingsystems and, more particularly, to wireless-enabled, portable devices.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more information handling systems, data storage systems,and networking systems.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and itsfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a block diagram of selected elements of an embodiment of acloud client device; and

FIG. 2 is an example of a network environment in which a cloud clientdevice may operate.

DESCRIPTION OF EXAMPLE EMBODIMENTS

In the following description, details are set forth by way of example tofacilitate discussion of the disclosed subject matter. It should beapparent to a person of ordinary skill in the field, however, that thedisclosed embodiments are exemplary and not exhaustive of all possibleembodiments.

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, entertainment,or other purposes. For example, an information handling system may be apersonal computer (e.g. desktop or laptop), tablet computer, mobiledevice (e.g. personal digital assistant (PDA) or smart phone), server(e.g. blade server or rack server), a consumer electronic device, anetwork storage device, or another suitable device and may vary in size,shape, performance, functionality, and price. The information handlingsystem may include random access memory (RAM), one or more processingresources such as a central processing unit (CPU) or hardware orsoftware control logic, ROM, and/or other types of nonvolatile memory.Additional components of the information handling system may include oneor more disk drives, one or more storage devices, one or morecommunications ports (e.g. network ports) for communicating withexternal devices as well as various input and output (I/O) devices, suchas a keyboard, a mouse, a touchscreen and/or a video display. Theinformation handling system may also include one or more buses operableto transmit communication between the various hardware components.

Herein, a computer-readable non-transitory storage medium or media mayinclude one or more semiconductor-based or other integrated circuits(ICs) (such as, for example, field-programmable gate arrays (FPGAs) orapplication-specific ICs (ASICs)), hard disk drives (HDDs), hybrid harddrives (HHDs), optical discs, optical disc drives (ODDs),magneto-optical discs, magneto-optical drives, floppy diskettes, floppydisk drives (FDDs), magnetic tapes, solid-state drives (SSDs),RAM-drives, SECURE DIGITAL cards or drives, any other suitablecomputer-readable non-transitory storage media, or any suitablecombination of two or more of these, where appropriate. Acomputer-readable non-transitory storage medium may be volatile,non-volatile, or a combination of volatile and non-volatile, whereappropriate.

Particular embodiments are best understood by reference to FIGS. 1-5wherein like numbers are used to indicate like and corresponding parts.

FIG. 1 illustrates an example information handling system 100. Inparticular embodiments, one or more information handling systems 100perform one or more steps of one or more methods described orillustrated herein. In particular embodiments, one or more informationhandling systems 100 provide functionality described or illustratedherein. In particular embodiments, software running on one or moreinformation handling systems 100 performs one or more steps of one ormore methods described or illustrated herein or provides functionalitydescribed or illustrated herein. Particular embodiments include one ormore portions of one or more information handling systems 100. Herein,reference to an information handling system may encompass a computingdevice, and vice versa, where appropriate. Moreover, reference to aninformation handling system may encompass one or more informationhandling systems, where appropriate.

This disclosure contemplates any suitable number of information handlingsystems 100. This disclosure contemplates information handling system100 taking any suitable physical form. As an example and not by way oflimitation, information handling system 100 may be an embeddedinformation handling system, a system-on-chip (SOC), a single-boardinformation handling system (SBC) (such as, for example, acomputer-on-module (COM) or system-on-module (SOM)), a desktopinformation handling system, a laptop or notebook information handlingsystem, an interactive kiosk, a mainframe, a mesh of informationhandling systems, a mobile telephone, a personal digital assistant(PDA), a server, a tablet information handling system, or a combinationof two or more of these. Where appropriate, information handling system100 may include one or more information handling systems 100; be unitaryor distributed; span multiple locations; span multiple machines; spanmultiple data centers; or reside in a cloud, which may include one ormore cloud components in one or more networks. Where appropriate, one ormore information handling systems 100 may perform without substantialspatial or temporal limitation one or more steps of one or more methodsdescribed or illustrated herein. As an example and not by way oflimitation, one or more information handling systems 100 may perform inreal time or in batch mode one or more steps of one or more methodsdescribed or illustrated herein. One or more information handlingsystems 100 may perform at different times or at different locations oneor more steps of one or more methods described or illustrated herein,where appropriate.

In particular embodiments, information handling system 100 includes aprocessor 102, memory 104, storage 106, an input/output (I/O) interface108, a communication interface 110, and a bus 112. Although thisdisclosure describes and illustrates a particular information handlingsystem having a particular number of particular components in aparticular arrangement, this disclosure contemplates any suitableinformation handling system having any suitable number of any suitablecomponents in any suitable arrangement.

In particular embodiments, processor 102 includes hardware for executinginstructions, such as those making up a computer program. As an exampleand not by way of limitation, to execute instructions, processor 102 mayretrieve (or fetch) the instructions from an internal register, aninternal cache, memory 104, or storage 106; decode and execute them; andthen write one or more results to an internal register, an internalcache, memory 104, or storage 106. In particular embodiments, processor102 may include one or more internal caches for data, instructions, oraddresses. This disclosure contemplates processor 102 including anysuitable number of any suitable internal caches, where appropriate. Asan example and not by way of limitation, processor 102 may include oneor more instruction caches, one or more data caches, and one or moretranslation lookaside buffers (TLBs). Instructions in the instructioncaches may be copies of instructions in memory 104 or storage 106, andthe instruction caches may speed up retrieval of those instructions byprocessor 102. Data in the data caches may be copies of data in memory104 or storage 106 for instructions executing at processor 102 tooperate on; the results of previous instructions executed at processor102 for access by subsequent instructions executing at processor 102 orfor writing to memory 104 or storage 106; or other suitable data. Thedata caches may speed up read or write operations by processor 102. TheTLBs may speed up virtual-address translation for processor 102. Inparticular embodiments, processor 102 may include one or more internalregisters for data, instructions, or addresses. This disclosurecontemplates processor 102 including any suitable number of any suitableinternal registers, where appropriate. Where appropriate, processor 102may include one or more arithmetic logic units (ALUs); be a multi-coreprocessor; or include one or more processors 102. Although thisdisclosure describes and illustrates a particular processor, thisdisclosure contemplates any suitable processor.

In particular embodiments, memory 104 includes main memory for storinginstructions for processor 102 to execute or data for processor 102 tooperate on. As an example and not by way of limitation, informationhandling system 100 may load instructions from storage 106 or anothersource (such as, for example, another information handling system 100)to memory 104. Processor 102 may then load the instructions from memory104 to an internal register or internal cache. To execute theinstructions, processor 102 may retrieve the instructions from theinternal register or internal cache and decode them. During or afterexecution of the instructions, processor 102 may write one or moreresults (which may be intermediate or final results) to the internalregister or internal cache. Processor 102 may then write one or more ofthose results to memory 104. In particular embodiments, processor 102executes only instructions in one or more internal registers or internalcaches or in memory 104 (as opposed to storage 106 or elsewhere) andoperates only on data in one or more internal registers or internalcaches or in memory 104 (as opposed to storage 106 or elsewhere). One ormore memory buses (which may each include an address bus and a data bus)may couple processor 102 to memory 104. Bus 112 may include one or morememory buses, as described below. In particular embodiments, one or morememory management units (MMUs) reside between processor 102 and memory104 and facilitate accesses to memory 104 requested by processor 102. Inparticular embodiments, memory 104 includes random access memory (RAM).This RAM may be volatile memory, where appropriate. Where appropriate,this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, whereappropriate, this RAM may be single-ported or multi-ported RAM. Thisdisclosure contemplates any suitable RAM. Memory 104 may include one ormore memories 104, where appropriate. Although this disclosure describesand illustrates particular memory, this disclosure contemplates anysuitable memory.

In particular embodiments, storage 106 includes mass storage for data orinstructions. As an example and not by way of limitation, storage 106may include a hard disk drive (HDD), a floppy disk drive, flash memory,an optical disc, a magneto-optical disc, magnetic tape, or a UniversalSerial Bus (USB) drive or a combination of two or more of these. Storage106 may include removable or non-removable (or fixed) media, whereappropriate. Storage 106 may be internal or external to informationhandling system 100, where appropriate. In particular embodiments,storage 106 is non-volatile, solid-state memory. In particularembodiments, storage 106 includes read-only memory (ROM). Whereappropriate, this ROM may be mask-programmed ROM, programmable ROM(PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM),electrically alterable ROM (EAROM), or flash memory or a combination oftwo or more of these. This disclosure contemplates mass storage 106taking any suitable physical form. Storage 106 may include one or morestorage control units facilitating communication between processor 102and storage 106, where appropriate. Where appropriate, storage 106 mayinclude one or more storages 106. Although this disclosure describes andillustrates particular storage, this disclosure contemplates anysuitable storage.

In particular embodiments, I/O interface 108 includes hardware,software, or both, providing one or more interfaces for communicationbetween information handling system 100 and one or more I/O devices.Information handling system 100 may include one or more of these I/Odevices, where appropriate. One or more of these I/O devices may enablecommunication between a person and information handling system 100. Asan example and not by way of limitation, an I/O device may include akeyboard, keypad, microphone, monitor, mouse, printer, scanner, speaker,still camera, stylus, tablet, touch screen, trackball, video camera,another suitable I/O device or a combination of two or more of these. AnI/O device may include one or more sensors. This disclosure contemplatesany suitable I/O devices and any suitable I/O interfaces 108 for them.Where appropriate, I/O interface 108 may include one or more device orsoftware drivers enabling processor 102 to drive one or more of theseI/O devices. I/O interface 108 may include one or more I/O interfaces108, where appropriate. Although this disclosure describes andillustrates a particular I/O interface, this disclosure contemplates anysuitable I/O interface.

In particular embodiments, communication interface 110 includeshardware, software, or both providing one or more interfaces forcommunication (such as, for example, packet-based communication) betweeninformation handling system 100 and one or more other informationhandling systems 100 or one or more networks. As an example and not byway of limitation, communication interface 110 may include a networkinterface controller (NIC) or network adapter for communicating with anEthernet or other wire-based network or a wireless NIC (WNIC) orwireless adapter for communicating with a wireless network, such as aWI-FI network. This disclosure contemplates any suitable network and anysuitable communication interface 110 for it. As an example and not byway of limitation, information handling system 100 may communicate withan ad hoc network, a personal area network (PAN), a local area network(LAN), a wide area network (WAN), a metropolitan area network (MAN), orone or more portions of the Internet or a combination of two or more ofthese. One or more portions of one or more of these networks may bewired or wireless. As an example, information handling system 100 maycommunicate with a wireless PAN (WPAN) (such as, for example, aBLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephonenetwork (such as, for example, a Global System for Mobile Communications(GSM) network), or other suitable wireless network or a combination oftwo or more of these. Information handling system 100 may include anysuitable communication interface 110 for any of these networks, whereappropriate. Communication interface 110 may include one or morecommunication interfaces 110, where appropriate. Although thisdisclosure describes and illustrates a particular communicationinterface, this disclosure contemplates any suitable communicationinterface.

In particular embodiments, bus 112 includes hardware, software, or bothcoupling components of information handling system 100 to each other. Asan example and not by way of limitation, bus 112 may include anAccelerated Graphics Port (AGP) or other graphics bus, an EnhancedIndustry Standard Architecture (EISA) bus, a front-side bus (FSB), aHYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture(ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, amemory bus, a Micro Channel Architecture (MCA) bus, a PeripheralComponent Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a serialadvanced technology attachment (SATA) bus, a Video Electronics StandardsAssociation local (VLB) bus, or another suitable bus or a combination oftwo or more of these. Bus 112 may include one or more buses 112, whereappropriate. Although this disclosure describes and illustrates aparticular bus, this disclosure contemplates any suitable bus orinterconnect.

In particular embodiments, information handling system 100 comprises acloud client device (CCD). A CCD may be a wireless-enabled, portabledevice that may include one or more processors 102 (e.g. dual core ARMprocessors), volatile memory 104 (e.g. RAM), non-volatile memory 104(e.g. flash memory), input/output interfaces 108 (e.g. for display, fordata, and for audio), networking/communications interfaces 110, and oneor more operating systems (e.g. stored in memory 104 and operated on byprocessors 102). The input/output interfaces 108 may include displayinterfaces that support one or more of the Mobile High-Definition Link(MHL) standard, the High Definition Multimedia Interface (HDMI)standard, or the Display Port (DP) standard. The input/output interfaces108 may also include one or more USB ports (e.g. standard, mini or microUSB), one or more removable memory slots (e.g. SD card slots), and audiocapabilities through the MHL, HDMI, or DP interfaces. The CCD mayinclude networking or communication interfaces 110 that support IEEE802.11 protocols (including a, b, g, or n), single or dual band WiFi,BLUETOOTH communication, and near field communication (NFC). The CCD mayinclude one or more operating systems, including versions of Android,Windows, Wyse ThinOS, Linux, or Apple iOS. The CCD may include one ormore native applications, including, for example, a browser, a mediaplayer and recorder, voice over IP and video communication software, andsoftware for remote access to cloud services or other remote content orservices. The CCD may plug directly into a device (e.g. a display devicesuch as a television, monitor, or projector), may be connected via acable (via one of the above-described interfaces) to a device, or may beconnected via a wireless interface to a device (e.g. a display or clientdevice). A user may, for example, use the CCD to securely communicate;access files or contents that are on the CCD, on another local device,or on a remote device (e.g. in a server of a cloud servicesorganization); or control, interact with, or mediate one or more localdevices (e.g. client devices) or remote devices (e.g. remote clientdevices). The CCD may be remotely provisioned, authenticated, andcontrolled including, for example, by a cloud service.

FIG. 2 illustrates an example network environment 200 in which a CCD mayoperate with other local or remote devices. In the example of FIG. 2,multiple devices and displays (e.g. elements 251, 252, and 254-258) arecommunicatively coupled (e.g. in any suitable wired or wireless fashion)to a network 240. Network 240 may be any suitable type of networkincluding, for example, an ad hoc network, a personal area network(PAN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), or one or more portions of the Internetor a combination of two or more of these network types. One or moreportions of network 240 may be wired or wireless. As an example, network240 may include portions of a wireless PAN (WPAN) (such as, for example,a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellulartelephone network (such as, for example, a Global System for MobileCommunications (GSM) network), or other suitable wireless network or acombination of two or more of these.

As shown in FIG. 2, Network 240 may allow devices and displays coupledto it (e.g. elements 251, 252, and 254-258) to communicate with a cloudservices system 260. Cloud services system 260 may, for example, includeone or more servers 262 and a data store 264 including one or more datastorage systems. Network 240 may also allow devices and displays coupledto it to communicate with each other. Although not illustrated in FIG.2, one or more of the devices and displays of network environment 200may, in particular embodiments, communicate with each other directly(e.g. wirelessly) or via any other suitable communication method.

In the example of FIG. 2, CCD 232 is coupled locally to computing device252, CCD 233 is coupled locally to display 253, and CCD 234 is coupledlocally to projector 258. As an example, CCD 232 may be wirelesslycoupled to computing device 252 (e.g. via BLUETOOTH), CCD 233 may becoupled to display 253 via, for example, a USB port, and CCD 234 may becoupled to projector 258 via, for example, HDMI. Additionally, CCD 232,CCD 233, and CCD 234 may each communicate (or be coupled) with oneanother or with one or more devices or displays (e.g. elements 251-258)locally or directly (e.g. via NFC or BLUETOOTH), via their respectivecoupled devices (e.g. 252, 253, 258), via network 240, or via any othersuitable communication method. Furthermore, CCD 232, CCD 233, and CCD234 may each communicate with network 240 directly via any suitablecommunication method, without need of being coupled to a device (e.g. adisplay or a computing device).

In particular embodiments, the CCD is enabled to provide a wireless,remote interface for multi-platform control and mediation of one or moreclient or display devices (e.g. 251-258). The wireless, remote interfaceprovided by the CCD may use any type of suitable wireless technology orstandard including, but not limited to, IEEE 802.11 (a), (b), (g), and(n), WPS (Wi-Fi Protected Setup), BLUETOOTH, 3G and 4G mobilecommunication, and NFC. The platforms for each of the client or displaydevices (e.g. 251-258) may be the same or different and may include (byway of example and without limitation) Apple iOS, Microsoft Windows,Android, Wyse ThinOS, or Linux. Furthermore, each of the client ordisplay devices (e.g. 251-258) may include a software applicationconfigured to interact with the CCD (e.g. 232, 233, or 234) or withother client or display devices.

The CCD may function with a client device (e.g. a keyboard, mouse,tablet, computer, or phone) and enable remote events at the clientdevice to interact with or control the CCD, a remote client device, or adisplay device (e.g. a television, projector, or monitor). As anexample, a wireless keyboard or mouse may be used with the CCD, with aremote display device displaying the input from the keyboard or mouse.As another example, CCD 233 may be coupled to display 253, and remotetouch events from tablet 256 may control what is displayed on display253. As another example, CCD 232 may be coupled to computer 252, andinput (e.g. data or I/O from peripherals) may be directed by CCD 232from computer 252 to display 253, tablet 256, and projector 258simultaneously. In particular embodiments, inputs from a single clientdevice (e.g. phone 254) may be communicated to the CCD (e.g. 232, 233,or 234), such that the user of the client device maintains control overthe CCD (and a display device coupled to the CCD, e.g., monitor ofcomputer 252, display 253, or projector 258), with the effect that theclient device acts as a flexible wireless input device for the CCD. Asan example, in a classroom setting, content displayed on an instructor'stablet client device (e.g. 256) may be shared with students via the CCD(e.g. 233) by having the display device (e.g. 253) simultaneouslydisplay or mirror the display of the instructor's tablet client device.The instructor may control the CCD via the tablet and manipulate thecontent shown on the display by using gestures (e.g. touch ormulti-touch), soft keyboards, or touchpad functionality on the tablet.

In other embodiments, multiple client devices (e.g. keyboards, mice,etc.) may be used with one CCD, with the inputs from one or more ofthese devices simultaneously being processed by the CCD and in somecircumstances displayed on one or more display devices. As an example,again in a classroom setting, an instructor may use a tablet clientdevice, a first student may use a smartphone soft-keyboard, and a secondstudent may use a BLUETOOTH keyboard, and the inputs from all of thesedevices may be received by a CCD and displayed on a display device suchas a monitor. As yet another example, multiple people using multipleclient devices (e.g. tablets or smartphones) may together play a singlegame (e.g. streamed from the Internet via the CCD) displayed on a singledisplay device, with the inputs from each of the devices going to theCCD.

In particular embodiments, the CCD may be enabled to function with oneor more multifunction display devices, such as multi-touch-enableddisplays and/or displays with integrated webcams, speakers, microphones,etc. As an example, if the CCD is paired with a touch monitor (e.g. viaa wired or direct plug-in connection to the monitor such asUSB/MHL/HDMI, or via BLUETOOTH, NFC, or any other wireless technology),the CCD may be configured to operate directly with the display device,allowing a user to input touch gestures directly on the display deviceand interact with data displayed on the display device by the CCD. Forexample, if the user is navigating a website using a browser via theCCD, and the CCD is paired with a touch display device, the user maydirectly touch the display device to interact with the website, and theCCD will recognize and properly process the touch inputs. In otherembodiments, the user may operate both a touch display device and one ormore separate client devices (e.g. mouse, keyboard, tablet, orsmartphone) simultaneously, such that the user may input data via any orall of the client devices or display devices.

In particular embodiments, the CCD may be enabled to function in aunified communications framework. As an example, the CCD may be enabledto function with services such as instant messaging (e.g. includingpresence information), telephony (e.g. IP telephony), videoconferencing, data sharing (including Interactive White Boards), IPTV,call control (e.g. for VoIP), speech recognition, and unified messaging.In particular embodiments, the CCD may be enabled to function with (e.g.send data to and receive data from) one or more display devices thatinclude cameras. As an example, if the CCD is paired with a televisionincluding a camera (e.g. a built-in camera or webcam), microphone (e.g.built-in or attached as a USB peripheral), and an audio out (e.g.built-in speakers or speakers attached as peripherals), the CCD may beconfigured to operate directly to allow a user to engage invideoconference calls. The configuration may, for example, occur inconjunction with a cloud services provider (e.g. cloud services system260), described further herein. As an example, the cloud servicesprovider may allow the CCD to set up a SKYPE session, and link the userof display 253 to another user via the videoconference. The CCD mayoperate with various types of display devices with various types offunctionality including, but not limited to, multi-touch gestures, GPSor other location data, audio functionalities (including microphones andspeakers), or camera input. In some embodiments, the CCD is enabled tocommunicate with such additional components of the multi-functiondisplay device via the same interface over which it sends displayinformation (e.g. MHL via an HDMI interface). In other embodiments, theCCD is enabled to communicate with such components via an interfacedistinct from the display interface (e.g. the CCD may send displayinformation to the display device via an HDMI connection and may receivemulti-touch input information from the display device via a separate USBconnection).

In particular embodiments, the CCD is enabled to provide a wireless,remote interface including gesture redirection (e.g. touch ormulti-touch gestures) or input/output redirection (e.g. of any suitabletype including those listed herein) in conjunction with one or moredevices. The CCD, for example, may provide a virtualized touchinterface. The CCD may function with a client device (e.g. a smartphone,tablet, laptop, etc.) to redirect multi-touch gestures from the clientdevice to control or otherwise interact with a display device or anotherclient device. For example, a user of a smartphone may swipe, fling, usemultiple-finger touch inputs (including, e.g., from a soft-keyboard),pinch-to-zoom, scroll, etc. on the smartphone. These multi-touchgestures may be received by the CCD (e.g. by a multi-touch clientreceiver) and used to control or interact with one or more displaydevices or client devices (e.g. via a multi-touch gesture proxycontroller and a native display driver of the display device). As anexample, input from one client device (e.g. a user's pinchingmulti-touch gesture at tablet 256) may be sent to a CCD (e.g. 232),which then exports the input to control the operation of another clientdevice (e.g. to cause a zoom in on an image displayed in a browserrunning on computer 252). In this example, the output displayed oncomputer 252 may then be sent to the CCD 232 and displayed on tablet256. As described above, multiple client devices may be used with oneCCD in certain embodiments, with the multi-touch inputs from one or moreof these devices being simultaneously displayed or used to control onone or more display or client devices.

The types of input gathered from client devices (e.g. 251-258) may beany type of input including, but not limited to, gestures (e.g. touch ormulti-touch gestures, described herein), keyboard input, mouse input,accelerometer input, gyroscope input, GPS or other location data, camerainput (video or still images), sound input (e.g. from a microphone), orinput from any suitable type of sensor including, e.g., acoustic, sound,vibration, chemical, electric, magnetic, radio, environmental,navigation, optical, pressure, temperature, or proximity sensors. Anysuitable input from a client device may be sent to a CCD, which may thensend this input to any other client device (including any peripheral orother component of the client device), display device, remote device,etc. As an example, a user's voice input at phone 255 may be sent to aCCD (e.g. 233) which then sends that voice data to be played on aspeaker at computer 251.

In particular embodiments, a CCD may be configured to translate inputsbetween devices. In this manner, resources, features, and functionalityof one device may be made available to another device via mediation bythe CCD using, for example, a transparent wireless transport protocol(e.g. WiFi or BLUETOOTH). For example, inputs received at a firstdevice, such as a smartphone, may be intercepted, communicated to theCCD, translated into a format understood by a second device orapplication, and provided to that second device or application. As anexample, a gesture or an input may be translated to multi-touch at adevice, and vice versa. As another example, voice input from a firstdevice (e.g. at a microphone) may be translated to text at a seconddevice, and vice versa. As yet another example, a gesture at a firstdevice (e.g. captured by a camera) may be translated to an action (e.g.scrolling) at a second device. In some cases, the device or applicationreceiving the remote inputs may be able to receive and process thoseinputs in their original format. In such cases, the inputs need notnecessarily be translated, but may be redirected by the CCD.

In particular embodiments, a CCD may be configured to provide virtualsensors (or other functionality) to a client device or display (e.g. ina manner similar to a virtual USB hub). As an example, if CCD 233 iscoupled (e.g. plugged into a USB port) with display 253, then CCD 233may dynamically construct a virtual set of sensors and other devices(e.g. 251, 252, and 254-258) for use by display 253. That is, CCD 233may determine what other devices (and what sensors on those devices) areavailable for pairing by, for example, conducting a scan to see if thelocal network contains pairable devices (e.g. devices within acommunication range for pairing). For those pairable devices, the CCD233 may request the devices to enter a pairing mode and then scan (e.g.NFC tags, or other pairing methods) to construct a model of availabledevices or sensors (e.g. a mesh). The CCD 233 may then pair those withdisplay 253 and provide functionality or services from those devices orsensors to display 253. As an example, CCD 233 may couple a phone (e.g.254) with display 253, such that if a user at display 253 using CCD 233needs her location information (e.g. to authenticate an account withcloud services system 260), the GPS module of phone 254 may beseamlessly used to provide location information and authenticate CCD233. In this manner, a user need not manually couple or otherwise pairlocal devices, download drivers manually, or do other manualconfigurations of CCD 233 or display 253.

In particular embodiments, the CCD may be enabled to operate inconjunction with cloud (or other remote or virtualized) services. Asexamples, the CCD may include software that enables it to function withthe Dell Wyse Cloud Client Manager or Dell Wyse PocketCloud software, orany other suitable remote or cloud service.

As an example, the CCD may be enabled to operate with a cloud service(e.g. 260) such as the Dell Wyse Cloud Client Manager (Dell CCM).Through the cloud service, the CCD may be remotely provisioned andauthenticated. The cloud service may provide, for example and withoutlimitation, access to data, applications, services, or remote desktops.

In particular embodiments, the CCD may be authenticated using a varietyof methods including WiFi Protected Setup (e.g. by using a WPS certifiedrouter to establish connectivity to the cloud service), an SD Card orUSB source (or any other local source) of a configuration file, or aclient device. As an example, a token stored on a particular clientdevice may be required to authenticate a user attempting to access aCCD. When the client device (e.g. a smartphone, tablet, laptop, etc.)supporting BLUETOOTH, NFC, or other wireless technology is brought intoproximity with the CCD, the CCD may obtain a secure or encrypted token(e.g. an RSA token) from the client device over the wireless interface.Once this secure token is obtained, the CCD may then authenticate itscredentials with the cloud service.

The CCD may, for example, send particular data to the cloud service forauthentication. The data may include, for example, the security token,location of the CCD (determined, e.g., based on data from a GPStransmitter of the CCD or MAC address scanning), an IP address of theCCD, a MAC address of the CCD, a usage log of usage behavior orstatistics associated with the CCD, software or hardware versions ofcomponents of the CCD, etc. Based on the data received from the CCD, thecloud service may construct a profile associated with the CCD (e.g.stored in data store 264) or, alternatively, find and analyze (e.g. viaservers 262) an existing profile associated with the CCD. For example,the CCD may be associated with a particular user of the cloud service,and particular security, authentication, quality-of-service, access,encryption, or other settings or data may be associated with the user inthe user profile for the cloud service. The profile associated with aCCD in the cloud service may be specific to a user associated with theCCD, an entity associated with the CCD (e.g. a corporate profile withcorporate settings), or any other individual, group of individuals, ororganization associated with the CCD. Furthermore, if the CCD is notassociated with a profile in the cloud service, the cloud service mayuse certain default settings to authenticate or provision the CCD.

In particular embodiments, when the cloud service receives data from theCCD, the cloud service may determine which user the CCD is associatedwith (e.g. based on a MAC address of the CCD), examine the profile forthis user, and authenticate and provision the CCD based on data in thisprofile. As an example, the cloud service may determine that the CCD isassociated with a user whose profile only allows cloud service accesswithin a particular geographical region. If, for example, the CCD ispresently in South America (as determined, for example, from the CCD'sIP address or by approximating the location of the CCD by analyzing thewireless networks within the range of the CCD), but the profile for theuser associated with the CCD allows CCD access to the cloud service anddata only within North America, then the cloud service may refuse toauthenticate the CCD. Any appropriate security measure may be enforcedby the cloud service based on data associated with the CCD or the cloudservice user profile. As another example, the user profile may includewhite- or black-lists that detail websites, cloud services orapplications that the user may be able to access (or may be deniedaccess to) depending on the location of the CCD or depending on otherinformation associated with the CCD (e.g. processes currently running onthe CCD).

In addition to allowing or denying access to cloud services orapplications, the CCD may be remotely wiped (e.g. to a reset or clearstate for re-imaging), locked, or queried (e.g. a query to determine thelocation of the CCD) by the cloud service, including, e.g., by a cloudservice administrator. In particular embodiments, the CCD may beremotely wiped if another client device (e.g. a smartphone) is notwithin a particular range of the CCD. In particular embodiments, aspecific standard method for wiping by overwriting the file system ofthe CCD may be employed such that the CCD may not be recoverable by athird party. This may be administered by the cloud service, or may beindependently deployed. The CCD may be completely wiped (e.g. to factorysettings) if certain conditions are met (e.g. if the cloud servicedetermines the CCD should be wiped). In other embodiments, the CCD maybe wiped in a manner that leaves all cloud-services-installedapplications on the CCD but removes everything else. In particularembodiments, certain zones of the memory or storage of the CCD may bewiped, and in other embodiments, the entire CCD may be wiped.

The CCD may be fully imaged and the operating system of the CCD may befully recovered via the cloud service even if the CCD is wiped or resetat an earlier time (e.g. by the cloud service for security reasons). TheCCD may have any type of profile settings, content, or connectionsautomatically pushed to it from the cloud service. The CCD may receivesystem updates from the cloud service including, for example, firmwareor application updates. These updates may be determined based oninformation in the cloud service profile associated with the CCD, aswell as information received from the CCD. The cloud service may alsomanage files on the CCD, as well as partition the CCD (e.g. intopersonal and corporate segments with separate profiles). The datatransferred between the CCD and the cloud service may, for example, beencrypted using standard encryption, proprietary encryption, or acombination of both types. The cloud service may implement variouspolicies or rules on the CCD after authenticating and provisioning theCCD. For example, the cloud service profile associated with a CCD mayinclude policies related to quality-of-service, such that the cloudservice may track data usage of the CCD and may implementquality-of-service data usage policies on the CCD. In addition to usingthe cloud service, the recovery of data on the CCD or the upgrading orupdating of software on the CCD may be accomplished in the followingways:

-   -   1) Manually via the CCD itself (e.g. using a wireless interface        in the CCD to automatically retrieve data, e.g., from a cloud        service or from the Internet)    -   2) Connecting the CCD to a PC (e.g. obtaining data stored on the        PC or using a web-based application on the PC to repair or        update the CCD without needing to download any data to the PC)    -   3) Using data stored on a MicroSD (or other type of storage)        card operable with the CCD, or    -   4) Using a purely web-based remote update mechanism to remotely        send data to the CCD.

The CCD may be operable to access other types of remote networks orservices, as well as cloud services. For example, the CCD may be fullypre-configured to access a virtual private network (VPN), for example bythe owner of virtual private network (e.g. a corporation whose employeesare issued pre-configured CCDs). Thus, in particular embodiments, theCCD may have automatic VPN provisioning without any need for user inputor configuration. The automatic VPN provisioning may occur, inparticular embodiments, through the authentication or provisioningprocess by a cloud service, described above, and may, for example,provision based on a user's profile. Additionally, in combination withother capabilities of the CCD described herein, a user at one locationon the VPN network may connect to services from a device at anotherlocation on the VPN network (e.g. a printer in a private officenetwork), allowing for any device to remote its functions over bothlocal networks and VPNs, as well.

In particular embodiments, the CCD may be enabled to operate withmultiple types of security protocols. As an example, the authenticationof the CCD by receipt of a security token from a client device viaBLUETOOTH or NFC (as described earlier in detail) may be a first levelof security. A second level may be imposed through a cloud serviceauthentication of the CCD (e.g. through the cloud service analysis ofdata provided by the CCD and through profile data associated with theCCD). Additionally, the links between the CCD and the cloud service (orany other links) may be encrypted using any suitable standard orproprietary encryption techniques. Finally, at any of these steps, a PINor log-in may be required for a particular user using the CCD, as it iscontemplated that multiple users may be associated with a single CCD, orthat a single user may have separate profiles (e.g. work and personal)for a single CCD.

These security measures may enable the CCD to act as a portable andsecure computing device even when highly confidential material isinvolved. Even if an unauthorized person obtains a CCD, obtains theclient device with the secure token required for authentication of theCCD, and obtains all necessary log-in information to operate the CCD,the owner of the CCD may remotely disable and/or wipe the memory of theCCD via a cloud service (e.g. via Dell CCM). Moreover, as mentionedabove, the CCD may be configured to automatically set up appropriateconnections and communications sessions upon initialization andauthentication, including automatic configuration of a VPN via a cloudservice. A CCD may thus be configured to automatically present the userwith a remote desktop (in conjunction with well-known virtualizationand/or cloud computing software, such as that provided by Citrix andVMWare) that is similar to or identical to the desktop environment onthe user's networked office computer. The CCD thus presents thepossibility of low-cost, highly portable, highly secure, and broadlycompatible computing.

The CCD may be enabled to operate with client-to-client software such asDell Wyse PocketCloud software. The client-to-client software may, inparticular embodiments, be used in conjunction with one or more cloud orremote services (e.g. the Dell Wyse Cloud Client Manager describedabove).

In particular embodiments, the CCD may be enabled to operate withclient-to-client software that enables the CCD to see, communicate with,and otherwise interact with (or control) other client devices and theircontents. As an example, multi-touch redirection, described above, maybe implemented using the client-to-client software on the CCD and otherdevices. As an example, the CCD may include an application that allowsthe CCD to discover and access content across multiple client devices.Each of the devices may, for example, run an instance of theapplication, and each device may recognize and access other devices overBLUETOOTH, IEEE 802.11, ad-hoc wireless networking, IP networks, 3G or4G connectivity, etc. The connection between these devices may, inparticular embodiments, need not ever go to a cloud service, theInternet, or any other remote network and may, for example, be doneentirely in a peer-to-peer fashion. In other embodiments, the connectionbetween these devices may occur in part over a remote network. Theclient-to-client software may, for example, include a browser (e.g.Chrome) that allows the CCD and other devices to share a single contentdisplay (e.g. a single streaming video) as well as to share the controlof content on one or more displays (e.g. a multi-player video game inwhich input is received from multiple client devices). Theclient-to-client software may allow the CCD and other devices to searchand share applications or files (including video, audio, etc.); streamfiles; or copy, move, and backup files among each other. Theclient-to-client software may also allow the CCD and other devices tocreate a shared drive that is either public or private. Theclient-to-client software may, for example, also include auto-discovery,network management, file management (e.g. download, upload, copy, move,delete, rename, stream, or preview, etc.), and file transcoding (e.g.pause, play, fast forward, rewind, etc.) capabilities. The CCD may actas a router or central point through which any or all of theclient-to-client activities or traffic may pass. In particularembodiments, the client-to-client software may also include anapplication (e.g. Dell Wyse Freezer, or any other HTML5 client) thatallow the client devices to access proprietary applications (e.g. aremote Windows desktop, applications, or files) via a web applicationbrowser.

The CCD may be a low-power device. The CCD may receive power inaccordance with the MHL 1.0 standard, or in accordance with subsequentrevisions of the MHL standard. This allows the use of a single physicalinterface that may both provide power to the CCD and serve as thecommunications interface between the display device and the CCD. Inother embodiments, the CCD may be powered via a separate interface, suchas a USB port (e.g. connected to the display device or to anotherUSB-enabled device), or via an A/C adapter. A CCD may also be configuredto be broadly compatible and to receive power via any of theseinterfaces, depending on which is available.

In particular embodiments, an organization (e.g. a corporation) may havemultiple client devices or display devices (e.g. digital signs orkiosks) that it wishes to use for one or more dedicated purposes. As anexample, some digital signs or kiosks may be used exclusively to displaybuilding maps, while others may be used to display only particularcontent (e.g. photos, videos, or presentations in a looped format). Asanother example, a digital kiosk may allow users to operate onlyparticular applications, such as a price look-up application or a cashregister application that allows a user to pay for purchases in acommercial setting. In particular embodiments, it may be desirable toconfigure a client device or display device to meet specific customrequirements (e.g. requirements of the organization) with respect tocontent or applications available for a user of the client device ordisplay device. The client device or display device (e.g. a digital signor kiosk) may, for example, run the standard version of the Androidoperating system, which may not already include required customizationsfor a particular organization. In other embodiments, the client deviceor display device may run no operating system at all (e.g. in the caseof a simple monitor).

In particular cases, customizing a client device or display device (e.g.a digital sign or kiosk) to specific requirements (e.g. of a particularorganization) when the device runs no operating system or only thestandard Android operating system may be difficult, error prone, orotherwise challenging. For example, on a standard commercial devicerunning the Android operating system with the addition of a customizedapplication (such as, e.g., a tablet or display device operating inkiosk mode), a user may press the “home” or “back” button on the device,allowing the user to gain full operating system access. The user maythen switch away from the custom application to access other areas ofthe device, which may be unwanted by the organization maintaining thedevice. Furthermore, a user may also be able to disable the networkconnections of the device (e.g. by putting the device in “airplanemode”), preventing the device from performing its intended functions forfuture users. Additionally, notifications sent to the device (e.g.operating system-level push notifications, network-originated pushnotifications, etc.) may also allow a user of the device to exit thecustomized application, which may be undesirable. If an organizationuses a vendor-provided management interface (e.g. to operate with MobileDevice Management (MDM) software) on each of its client devices ordisplays, this may require added expense, and may also limit the choiceof Android hardware that may be used, as each vendor and product mayhave only certain management features. Finally, if an organizationchooses to use a custom firmware solution for each of its client devicesor displays, this may entail even more added time and expense.

In particular embodiments, a CCD may function with a client device or adisplay device including, for example, a digital sign or a kiosk. TheCCD may be configured according to specific or custom requirements, suchthat the client device or display device may function as desired (e.g.as a digital sign or kiosk). This may be done in a single stepconfiguration process, potentially across multiple CCDs or devices,potentially alleviating one or more of the problems discussed hereinwith respect to configuring client devices and display devices. This mayalso be done in a manner that prevents malicious configuration attemptsby providing the option of encrypted configuration data.

In particular embodiments, a custom configuration including content,policies, and applications may be applied from a storage medium (e.g. anSD card, a USB drive, or an external hard disk) or from a remotelocation (e.g. a cloud services system or a network location) to a CCDoperating with a client device or display device (e.g. a tablet, amonitor, a television, etc.). In particular embodiments, the storagemedium may be coupled to a CCD, and the CCD may be coupled to the clientdevice or display device. Although the description herein focuses on theembodiment in which a CCD is coupled to a client device or displaydevice, in yet other embodiments, the storage medium may be connecteddirectly to the client device or display device (e.g. a tablet).

The configuration of a CCD (e.g. coupled to a client device or displaydevice) for the first time proceeds as follows. First, the CCD monitorsconfigurations events (e.g. the insertion of an SD card or other form oflocal storage, or the receipt of a configuration file from a networklocation or a cloud services system). The CCD then determines if aconfiguration event (e.g. a new configuration) is detected. The veryfirst time the CCD detects a configuration event in its operatinglifetime (e.g. before the CCD is custom-configured), the CCD obtains asecurity key associated with this first custom configuration and storesthis security key. The CCD is then configured using the content,applications, and policies presented in the custom configuration. Thecustom policies may be determined by the organization in control of theCCDs and may including any suitable policies such as, e.g., applicationwhitelists or blacklists, particular operational behaviors (such asignoring Android-default behaviors like going to a lock-screen after aperiod of inactivity), preventing a user from being able to accessdevice settings, preventing a user from being able to modify theoperation of the device, etc. After its original configuration, in thefuture, any time the CCD detects a configuration event (e.g. theinsertion of an SD card or the receipt of a configuration wirelessly)the CCD proceeds through an authentication process in which the securitykey presented in the present configuration is compared to the storedsecurity key associated with the original configuration. Only when thesecurity key of the present configuration matches that of the storedconfiguration will the CCD be reconfigured with the newly-presentedconfiguration. In addition to the security key (which may include anysuitable security key including, for example, a token or code) the CCDmay require one or more passwords or other forms of authenticationbefore allowing itself to be reconfigured. In this manner, anorganization may ensure that only authorized users and authorizedconfigurations may be applied to CCDs (and the client devices or displaydevices they operate with). As another security precaution, the CCD mayinclude time- or event-based security key removal to prevent leakage ofsecurity keys. For example, if an SD card including a configuration (anda configuration key) is left in a CCD for more than a threshold amountof time (e.g. 15 minutes), the CCD may invalidate this key and may, forexample, communicate to a cloud services system or central server (or toother CCDs directly) that the key has been compromised and is invalid.This can prevent unauthorized access to a security key. Similarly, if aparticular event is detected (e.g. from a pre-defined category of eventsassociated with unauthorized access), then the CCD may again invalidatethe key associated with the current configuration. As yet anothersecurity precaution, the configurations themselves may be encrypted, andthe CCD alone may perform decryption of the configuration files,preventing an unauthorized party from intercepting the configuration(e.g. including the case in which the configuration is wirelesslytransmitted to the CCD from a cloud services system or a remote networklocation).

In this manner, any time an organization wishes to update content,applications, or policies (including, e.g., providing new Wi-Fipasswords) on its CCDs (including those devices to which the CCDs arecoupled—such as digital signs or kiosks), the organization may simplyprovide updated content, applications, or policies in configurations,either in local storage form (e.g. SD cards that are physically coupledto the CCDs) or across a network (e.g. deploying the updates via a cloudservices system or from a network location). In particular embodiments,a cloud services system will send notifications (e.g. events via a cloudmessaging system) to the CCD that notify the CCD of new configurations,or the CCD may be instructed to check-in at some periodic interval withthe cloud services system to verify its current configuration anddetermine whether a new configuration is needed.

In order to enable an Android-based CCD coupled to a client device ordisplay device to be customized to perform only certain functions via acustom configuration as described herein, particular modifications maybe made to the standard Android operating system. First, the standardAndroid start-up sequence may be modified such that a local, externalfile system (including, e.g., an SD card, a USB drive, a hard drive, orany other suitable storage including a file system) may be queried bythe CCD coupled to the client device or display device before any userinteraction is recognized or any applications are launched. Thisprevents the situation in which a user attempts to interact with the CCDbefore it is properly configured, e.g., via a local storage. Second, thestandard Android network-connectivity sequence is modified such that theCCD may look for network-based boot options (e.g. DHCP or PXE bootoptions) before any user interactions are recognized or any applicationsare launched. Third, the Android boot loader of the CCD may be securedor locked, such that modifications may not be allowed by an unauthorizeduser. Furthermore, the “home” screen (or “launcher”) of the Androidoperating system may also be modified. In the standard Android operatingsystem, when the CCD starts up, the launcher is the first applicationavailable for user interaction, and it is also the application thatremains visible when all other applications are closed. In particularembodiments, the launcher may be modified to start system services thatcheck if a configuration is available on any data transport medium (e.g.SD card, USB drive, hard drive, network location, etc.). If a newconfiguration is discovered, then a management library is called.Additionally, in particular embodiments, after 15 minutes of run timewith a particular security key (e.g. specific to the CCD's originalconfiguration), the security key may be deleted from the CCD to improvesecurity.

Herein, “or” is inclusive and not exclusive, unless expressly indicatedotherwise or indicated otherwise by context. Therefore, herein, “A or B”means “A, B, or both,” unless expressly indicated otherwise or indicatedotherwise by context. Moreover, “and” is both joint and several, unlessexpressly indicated otherwise or indicated otherwise by context.Therefore, herein, “A and B” means “A and B, jointly or severally,”unless expressly indicated otherwise or indicated otherwise by context.

The scope of this disclosure encompasses all changes, substitutions,variations, alterations, and modifications to the example embodimentsdescribed or illustrated herein that a person having ordinary skill inthe art would comprehend. The scope of this disclosure is not limited tothe example embodiments described or illustrated herein. Moreover,although this disclosure describes and illustrates respectiveembodiments herein as including particular components, elements,feature, functions, operations, or steps, any of these embodiments mayinclude any combination or permutation of any of the components,elements, features, functions, operations, or steps described orillustrated anywhere herein that a person having ordinary skill in theart would comprehend. Furthermore, reference in the appended claims toan apparatus or system or a component of an apparatus or system beingadapted to, arranged to, capable of, configured to, enabled to, operableto, or operative to perform a particular function encompasses thatapparatus, system, component, whether or not it or that particularfunction is activated, turned on, or unlocked, as long as thatapparatus, system, or component is so adapted, arranged, capable,configured, enabled, operable, or operative.

What is claimed is:
 1. A method of a cloud client device comprising:monitoring for one or more configuration events of the cloud clientdevice; identifying a configuration event from the one or moreconfiguration events; identifying a configuration associated with theconfiguration event; determining a first security key associated withthe configuration; comparing the first security key with a storedsecurity key associated with a previous configuration; configuring thecloud client device in accordance with the configuration based, at leastin part, on the comparison of the first security key and the storedsecurity key, wherein the configuration comprises at least anapplication; preventing user access to one or more settings of the cloudclient device based, at least in part, on the configuration; comparingan amount of time associated with a presentation of the first securitykey to a predetermined threshold amount of time; wherein theconfiguration event is caused by connection of a local storage device tothe cloud client device; comparing an amount of time that the localstorage device has remained connected to the cloud client device since apresentation of the first security key by the local storage device to apredetermined threshold amount of time; invalidating the first securitykey based on the comparing of the amount of time; and communicating to acloud services system the invalidation of the first security key.
 2. Themethod of claim 1, further comprising communicating with a digital signor kiosk.
 3. The method of claim 1, further comprising: storing theconfiguration, wherein the configuration is stored on at least one ofthe following: a USB device coupled to the cloud client device; an SDcard coupled to the cloud client device; or a hard disk coupled to thecloud client device.
 4. The method of claim 1, wherein the configurationcomprises one or more of the following: one or more applications;digital content; or one or more policies.
 5. The method of claim 1,wherein the stored security key is associated with the originalconfiguration of the cloud client device.
 6. The method of claim 1,wherein the configuration event is associated with the insertion of anSD card comprising a configuration of a pre-determined type into thecloud client device.
 7. A method of a cloud client device comprising:monitoring for one or more configuration events of the cloud clientdevice; identifying a first configuration event from the one or moreconfiguration events; identifying a first configuration associated withthe first configuration event; storing a first security key associatedwith the first configuration; identifying a second configuration eventfrom the one or more configuration events; identifying a secondconfiguration associated with the second configuration event, wherein asecond security key is associated with the second configuration;configuring the cloud client device in accordance with the secondconfiguration based, at least in part, on a comparison of the firstsecurity key and the second security key, wherein the configurationcomprises at least an application; preventing user access to one or moresettings of the cloud client device based, at least in part, on thesecond configuration; wherein the second configuration event is causedby connection of a local storage device to the cloud client device;comparing an amount of time that the local storage device has remainedconnected to the cloud client device since a presentation of the secondsecurity key by the local storage device to a predetermined thresholdamount of time; invaliding the second security key based on thecomparing of the amount of time; and communicating to a cloud servicessystem the invalidation of the second security key.
 8. The method ofclaim 7, wherein the cloud client device communicates with a digitalsign or kiosk.
 9. The method of claim 7, further comprising: storing theconfiguration, wherein the second configuration is stored on at leastone of the following: a USB device coupled to the cloud client device;an SD card coupled to the cloud client device; or a hard disk coupled tothe cloud client device.
 10. The method of claim 7, wherein the secondconfiguration comprises one or more of the following: one or moreapplications; digital content; or one or more policies.
 11. The methodof claim 7, further comprising restricting user access to one or morefunctions of the cloud client device.